Skip to content

Switch to React functional components#307

Open
wilkie wants to merge 3 commits intomainfrom
switch-to-function-components
Open

Switch to React functional components#307
wilkie wants to merge 3 commits intomainfrom
switch-to-function-components

Conversation

@wilkie
Copy link
Copy Markdown
Contributor

@wilkie wilkie commented Apr 9, 2026

Fairly straight-forward conversion. Though it chose to make them in the form function MyComponent(...) {} and I would prefer const MyComponent = ({...}: MyComponentProps) => {...} instead. I will convert this in the TypeScript path.

@wilkie wilkie changed the base branch from main to upgrade-react-and-eslint April 9, 2026 04:27
@wilkie wilkie changed the base branch from upgrade-react-and-eslint to main May 7, 2026 20:38
Comment thread package.json
Comment on lines +52 to 54
"react": "18",
"react-dom": "18",
"react-papaparse": "^3.8.0",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are exact pins, which we shouldn't use. Although not necessarily important because when we bring it to frontend, we'd use the catalog version instead. I'd prefer we use a more relaxed semver, but I leave that up to you if we are going to inline to the main repo soon.

return () => {
clearInterval(animationTimer);
};
}, []); // eslint-disable-line react-hooks/exhaustive-deps
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Comment why or refactor to avoid?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants